Network Support Library/RoseWare - Network Support Library.iso/email/window.v2

Text File | 1993-10-09 | 36KB | 846 lines

REF: WINDOWS
                     Using Notework with MS-Windows 3.0 - 3.1

To run Notework for MS-Windows, MS-Windows itself must be set up to run
correctly on NetWare.  The following is a compilation of advice, with
planning advice followed by troubleshooting ideas.

=====Requirements Summary for MS-Windows 3.1 and 3.0=====

* SYSTEM.INI File
  The line "network=" must include "vnetware386"

* File Dates (Newer files may be available on CompuServe)
  These reside in the Windows system directory.  If the user is running
  in a local Windows directory (e.g.  a local hard disk), there will be
  a SYSTEM subdirectory where these files should be located.  If the user
  is running MS-Windows off the network, the Windows system directory will
  be on the user's path, and these files can be found there.

     - VNETWARE.386    3/10/92
     - VIPX.386        3/10/92

=====Requirements Summary for MS-Windows 3.0=====

* SYSTEM.INI File
  Must include the line "device=vpicda.386"

* Windows Control Panel/Network Icon
  Device Driver version must be 1.02 or greater

When using MS-Windows 3.0, be aware that several of the files required
to make MS-Windows work with NetWare are not shipped with MS-Windows.
MS-Windows 3.1 does, however, ship with the correct drivers to work on a
Novell network.  Novell also makes these files available on CompuServe
for download in a file WINUP4.ZIP located in the NOVLIB forum.

=====Problems Encountered in Using Notework=====

PROBLEM:
Screen "locks up" or freezes.
SOLUTION:
Check to make sure the CONFIG.SYS file has a "files=65" or greater
setting.  This is a parameter recommended by Microsoft for optimal
MS-Windows operation in a Network environment.
SOLUTION:
Also make sure that the Workstation's IPX and NETX versions are the
most recent releases.  Currently, IPX is at version 3.10 and NETX is
at Version 3.22 Rev.  A.
SOLUTION:
Finally, try loading the utility TBMI2.COM before entering MS-Windows.  This
is a Task Switcher Buffer Manager from Novell which ships with MS-Windows
3.1.  (Usually found in the WINDOWS\SYSTEM directory after setup).

PROBLEM:
Notework background has lines of "aaaaaaa" when popped up.
CAUSE:
Some video monitors (8514's in particular) install with a special driver on
the OEMFONTS.FON= line in the SYSTEM.INI file.  This driver puts an "a"
character on the screen instead of a space for a background.
SOLUTION:
Change the OEMFONTS line in the SYSTEM.INI file back to the original driver
with:  OEMFONTS.FON=VGAOEM.FON

PROBLEM:
Incorrect background color or pattern when restoring screen after
"popping down" Notework.
SOLUTION:
Font problems when restoring the screen from the Notework session are
usually linked to the availability of a system font. One solution is
to make sure there is at least one standard system font in the
SYSTEM.INI file.

PROBLEM:
Under MS-Windows there may be problems with VGA displays when using QEMM and
Notework.
CAUSE:
(Taken from MS-Windows' READ.ME file)

VGA Display Adapters:
If you use a VGA-compatible display adapter and have
difficulties running MS-Windows in 386 enhanced mode, you
might need to include the following line in the [386Enh]
section of your SYSTEM.INI file:

  EMMEXCLUDE=C400-C7FF

This is because some VGA compatible cards use additional
memory to enhance the performance of their cards.
Manufacturers of these cards include Video 7 and Paradise.
Display adapter boards with the main chip(s) manufactured
by Tseng Labs, Chips & Technologies, Paradise, and
Headland Technologies also function this way.

When MS-Windows is running in 386 enhanced mode and is
configured for VGA, MS-Windows detects most of these cards
and automatically excludes the additional memory.  However,
you must add the line to SYSTEM.INI yourself if:

  - You have both an 8514 and a VGA display adapter and
    configured MS-Windows for the 8514.

  - You have an enhanced VGA adapter that MS-Windows does
    not recognize.

See the SYSINI.WRI on-line document for the procedure.

*  If you have both a VGA display adapter (primary) and an
   8514 (secondary), you might have problems switching between
   full-screen non-Windows applications when running MS-Windows
   in 386 enhanced mode.

If an application does not display properly, the digital
to analog converter (DAC) on your VGA card needs to be
updated.  Contact the manufacturer for an upgrade.

In the meantime, if your application has a command to
refresh the screen, you might be able to temporarily
correct the display so you can use the application.  For
example, if your display is a color display, you can type
the following at the DOS Prompt and press ENTER:

                   MODE CO80

===== RUNNING MS-Windows ON A NOVELL NETWORK
      SOME TIPS FROM MICROSOFT =====

MS-Windows version 3.1 includes updated versions of several Novell NetWare
files that are required to run with MS-Windows 3.1.  If you are running Novell
NetWare, MS-Windows Setup will copy the following files to the SYSTEM
subdirectory of your Windows directory (or the shared network directory if you
set up a shared copy of MS-Windows by using setup /n).

NETX.COM (version 3.26) NETX.COM will run on MS-DOS versions 3.1 or higher.
   IPX.OBJ (version 3.10)
   TBMI2.COM (version 2.1)
   IPXODI.COM (version 1.20)
   LSL.COM (version 1.21)

IMPORTANT: The EMS NetWare shells (EMSNETX.EXE, etc.) are not supported when
MS-Windows is running in 386 enhanced mode.

If you are running Novell IPXODI.COM and LSL.COM, you need to upgrade these to
versions 1.20 or higher.  Use the files provided with MS-Windows and copy them
from the SYSTEM subdirectory of your Windows directory (or your shared network
directory) to the directory where your existing versions are located.

If you experience problems starting applications while running MS-Windows or
MS-Windows applications from a file server, make sure you are not running the
MS-DOS SHARE utility.  Current versions of the NetWare shell are not fully
compatible with SHARE.

To run MS-Windows in standard mode, load the TBMI2.COM memory-resident utility
when running MS-Windows.  Novell recommends that you create a batch file that
will load this utility, start MS-Windows, and then unload the utility when you
quit MS-Windows.  The batch file could be named RUNWIN.BAT and look like this:

   TBMI2
   WIN
   TBMI2 /U

TBMI2 enables you to safely run applications that use the NetWare IPX and SPX
functions in standard mode MS-Windows or the MS-DOS 5.0 task switcher.

If you enable 32-bit disk access and you are running the XMS shell rather than
one of the standard NetWare shells (NETX.COM, etc.), you can further improve
performance by setting the OverlappedIO entry in the [386Enh] section of your
SYSTEM.INI file to on.

Do not try to log in, log out, attach, or detach a Novell server from MS-DOS
Prompt within MS-Windows.  You should log in before starting MS-Windows, and
attach or detach servers by using File Manager or the Printers option in
Control Panel.

If you have a Western Digital Ethercard Plus and have problems accessing
drives by using the MAP ROOT command, contact Western Digital for an updated
driver.

By default, NetWare gives you access to only 40 files at a time.  When you are
running applications with MS-Windows, you can exceed this limit rather
quickly. If so, you might see unexpected error messages.  To increase the file
access limit, add the following line to your SHELL.CFG file:

   file handles = 60

You should also add the following to your CONFIG.SYS file:

   files = 60

If you get unusable output when printing to a NetWare server (such as
incorrect fonts, garbled text, invalid page breaks, or blank lines), you may
need to edit your print-job configuration.  Try using the NetWare PRINTCON
utility to set the Auto Endcap and Enable Timeout options to No.

When setting up MS-Windows for use with Novell NetWare, the following entry is
added to the [windows] section of your WIN.INI file:

   load=nwpopup.exe

This automatically starts the NetWare pop-up utility, which displays your
incoming broadcast (NOVELL SEND) messages.

If you are running Novell NetBIOS, you may need to specify
TimerCriticalSection=10000 in the [386Enh] section of the SYSTEM.INI file.

HOW TO CHECK YOUR SYSTEM DRIVERS

There are several checks which can be performed to verify that
the correct NetWare drivers are being used.  The simplest is to
open the Windows Control Panel, open the Network icon, then look
to see that the Device Driver version is 1.02 or greater.

Checking the Device Driver Version:

   1) Double-click the control panel icon in the appropriate group
      (usually MAIN) in the program manager, or type in "control"
      after selecting Run from the File menu in the program
      manager.
   2) Double click the Network Item in the control panel window.
   3) Check the Device Driver version.
   4) Click on Cancel, then close the control panel window.


Checking the SYSTEM.INI File:

  The next check is to make sure that SYSTEM.INI contains the
  correct references to the NetWare modules.  This will be done
  using an undocumented MS-Windows utility called SYSEDIT, which
  allows the user to examine and modify WIN.INI, SYSTEM.INI,
  CONFIG.SYS and AUTOEXEC.BAT.

  1) Type in "SYSEDIT" after selecting Run from the File menu in
     the program manager.  SYSEDIT should start up with four sub-
     windows.  (if the user is booting from the network,
     AUTOEXEC.BAT and CONFIG.SYS might not be found; you can
     ignore the warnings)
  2) Select the SYSTEM.INI sub-window.  Scroll down until you see
     the line "[386Enh]"
  3) Scroll down until you see a line which begins "network=".
     this line should contain "vnetware386" (it will also contain
     other things, probably "*vnetbios")
  4) There are many line which begin "device=".  One of these
     lines should contain "vpicda.386" (the 'a' in "vpicda" is
     critical).
  5) Close SYSEDIT.

Printing through MS-Windows on the Network (MS-Windows 3.0):

  Another potential trouble spot is in printing on the network.  Microsoft
  has released a version of MS-Windows, called "3.00a", which is supposed to
  fix problems in this area.  The MS-Windows version number can be found by
  selecting "About Program Manager" from the Help menu in the program
  manager.  Incidentally, this is also the way to discover in what mode
  MS-Windows is running (Real, Standard, 386 Enhanced), and how much memory is
  available.

  Printing problems are likely to be caused by incorrect settings in the
  user's print job configuration.  This can be changed with the NetWare
  PRINTCON utility.  The correct settings are "Auto Endcap" = No and
  "Enable Timeout" = No.  If these changes don't fix the problems, and the
  user is running MS-Windows 3.00 (no 'a'), version 3.00a can be obtained from
  Microsoft.

=====MS-Windows vs. NetWare Troubleshooting Tips=====
Compiled by Brett Warthen (Infinite Technologies)
                          July 15, 1992

The most important troubleshooting tip for solving conflicts
between MS-Windows and NetWare is to remember to use logical
deduction and the process of elimination to isolate conflicts.

For example, if you are using a 3rd party memory manager like
QEMM or 386-to-the-MAX, de-install it and try your configuration
running Microsoft's HIMEM.SYS that ships with MS-Windows 3.1 instead
(try without EMM386).  Then, if the problem is related to your
memory manager, you should contact that vendor for technical
support suggestions.

If you are loading any additional TSRs or device drivers, try
your configuration without them loaded, and add them back into
your system one by one to determine which is causing the
conflict.

If you are using EMSNETX or XMSNETX, try using regular old NETX
instead.

While far from being a comprehensive guide to all possible
MS-Windows and NetWare conflicts, this document contains some
troubleshooting tips for common problems running MS-Windows in the
NetWare environment.

Recommendations for ALL Systems:

     1.)  In the MS-Windows SYSTEM.INI file, verify the following
          settings:

          Under the [boot] section header:
          network.drv=netware.drv

          Under the [386Enh] section header:
          network=*vnetbios,vnetware.386,vipx.386

          (NOTE: *vnetbios can cause some problems with the
          current IBM LAN Support drivers.)

     2.)  Update to the latest NetWare drivers, a minimum level
          of IPX v3.10 (or IPXODI v1.20) and NETX v3.26 for
          proper support of the MS-Windows 3.1 environment.

     3.)  Check for duplicate copies of the NWPOPUP.EXE,
          VNETWARE.386, VIPX.386 and NETWARE.DRV files.  (You may
          find one version in the Windows directory and another
          in Windows\SYSTEM.)  Make sure that the only versions
          that remain on your system are 1992 dated versions.
          (The latest versions are on the MS-Windows 3.1 diskettes,
          but you many have to manually expand them.  Or you can
          download WINUP6.ZIP from NOVLIB Library 5 on
          CompuServe/NetWire.)

     4.)  Verify that the NETWARE.DRV file is approximately
          125,000 bytes in size.  We've seen plenty of problems
          where installation routines did not properly expand
          this file.

          The NetWare DOS/Windows Workstation Kit NWSETUP
          installation procedure is particularly notorious for
          this type of problem.

     5.)  Use WINSTART.BAT with care.  There is a bug with
          WINSTART.BAT processing under MS-Windows 3.1 on some PCs,
          which can cause MS-Windows to hang-up when exiting.

          The NetWare DOS/Windows Workstation Kit NWSETUP
          installation procedure creates a dummy WINSTART.BAT
          which can trigger this problem.

     6.)  If you want to receive broadcast messages while in
          MS-Windows, then make sure that NWPOPUP.EXE is included in
          the "load=" statement in your WIN.INI file.

     7.)  In your NET.CFG (or SHELL.CFG) file, be sure to
          allocate plenty of file handles.  FILE HANDLES=80 is a
          recommended minimum.

     8.)  In your NET.CFG (or SHELL.CFG) file, allocate
          additional stacks for IPX/SPX usage by specifying GET
          LOCAL TARGET STACKS = 5.

          The default setting is 1 stack, which can lead to
          system lockup problems when receiving NetWare broadcast
          messages.

          If you plan on making use of IPX/SPX applications on a
          regular basis, then you should increase this value to
          GET LOCAL TARGET STACKS = 10.

     9.)  If you are running DR-DOS 6, make sure that you have
          the April Business update installed for MS-Windows 3.1
          compatibility.

          This file can be downloaded from DRFORUM on CompuServe,
          DR6UP2.EXE in Library 2.

     10.)  If you are attempting to use the Burst Mode shell
          (BNETX) with MS-Windows 3.1, be aware that there are known
          conflicts that can cause severe system slowdowns and
          lockups with the current revision of this shell (v3.26)
          with many LAN drivers.

MS-Windows hangs while loading:

     1.)  For MS-Windows 3.0, is your network card set to IRQ 2 or
          9, 10 or higher?  If it is, then you will need to
          install the VPICDA.386 patch (included in WINUP6.ZIP in
          NOVLIB on CompuServe).  Copy VPICDA.386 into your
          Windows\SYSTEM directory, and edit your SYSTEM.INI,
          replacing the line "device=*vpicd" with
          "device=vpicda.386".

          NOTE:  VPICDA.386 is not required for MS-Windows 3.1, you
          should specify "device=*vpicd" instead.

     2.)  Try loading MS-Windows with a command-line parameter of
          /D:XSV (e.g., WIN /D:XSV).

          Each of the letters following the /D: are equivalent to
          placing the following statements under the [386Enh]
          section header in SYSTEM.INI, one time only:

          X -> EMMExclude=A000-EFFF
          S -> SystemRomBreakpoint=OFF
          V -> VirtualHDIrq=OFF

          If MS-Windows now works, use a process of elimination to
          determine which of the parameters was the key to your
          success.

          WIN /D:X is most often the solution to these types of
          problems, which indicates that the shared RAM area used
          by your network adapter is not properly excluded from
          your memory manager, or the MS-Windows internal memory
          manager.

          For MS-Windows internal memory manager, you exclude this
          memory range with an EMMExclude=xxxx-xxxx statement
          under the [386Enh] section header of your SYSTEM.INI.
          If you are unsure of this range, use EMMExclude=A000-
          FFFF while troubleshooting.  As an example, to exclude
          a 16KB range of memory at segment D000h, you would
          specify EMMExclude=D000-D3FF.

          For the Microsoft EMM386.EXE memory manager, use a
          /X=xxxx-xxxx parameter to tell it what range of memory
          to exclude for your network card.

     3.)  Are you loading MS-DOS 5 SHARE or running MS-DOS 4 (DOS
          4 automatically loads SHARE if you have a hard disk
          larger than 32MB)?

          If you can avoid loading SHARE, do so.

          If you cannot, load SHARE before IPX and NETX.  Place
          the statement "FILES=XXX" in your CONFIG.SYS file.  XXX
          is 255 minus 2 (reserved handles) minus the number of
          files handles defined in your NET.CFG (or SHELL.CFG)
          file.  The default is 40.  Therefore, if you are using
          the default, you would set FILES=213 in your
          CONFIG.SYS.

     4.)  There are known conflicts between the IBM LAN Support
          drivers for Token Ring and the "*vnetbios" driver
          supplied with MS-Windows.

          If you can use the NetWare drivers that talk directly
          to the Token Ring adapter, this should work.
          Otherwise, do not include "*vnetbios" on the "network="
          line under the [386Enh] section header of your
          SYSTEM.INI file, and avoid running any applications
          that use NETBIOS under MS-Windows.

     5.)  Are you loading SuperStor 2.0, a disk compression
          device driver?  There is a deadlock problem between
          NETX v3.26 and SuperStor 2.0 under MS-Windows.  As a
          temporary work-around, use the NETX v3.22 shell and
          contact the software manufacturer for other possible
          work-arounds.

     6.)  There could be an interrupt or I/O conflict between
          your network card, and MS-Windows searching your COM ports
          for a mouse.

          These are the default COM port interrupt (IRQ) & I/O
          assignments:

          COM1 = IRQ 4, I/O 3F8h
          COM2 = IRQ 3, I/O 2F8h
          COM3 = IRQ 4, I/O 2E8h
          COM4 = IRQ 3, I/O 2E0h

          (NOTE:  On IBM PS/2s, the settings for COM3 or COM4 are
          different.)

          In the [386Enh] section header of SYSTEM.INI, you can
          specify COM#Irq=-1 to disable a particular port.  For
          example, specify COM2Irq=-1 to disable COM2.

          You could also specify MaxCOMPort=2 under the [386Enh]
          section header to ensure that COM3 and COM4 are not
          being used.

System Hang-ups running RCONSOLE or other IPX/SPX applications
under MS-Windows:

     1.)  Verify that you have all of the latest drivers for
          running IPX/SPX under MS-Windows.

          A minimum version level of IPX v3.10 or IPXODI v1.20 is
          required.

          For MS-Windows in 386 Enhanced Mode, make sure that you
          have VIPX.386 v1.10 or v1.11.  (Use the NetWare VERSION
          utility to run against VIPX.386 to determine the
          version.)  Make sure that you do not have duplicate
          copies of VIPX.386 elsewhere in your path.  In
          particular, check both the Windows and Windows\SYSTEM
          directories for duplicates.  Furthermore, ensure that
          VIPX.386 is included in the "network=" statement under
          the [386Enh] section header of your SYSTEM.INI.

          For MS-Windows in Standard Mode, make sure that TBMI2 is
          loaded before going into MS-Windows, but this will not be
          sufficient for many IPX/SPX applications.

     2.)  Place the statement GET LOCAL TARGET STACKS = 10 in
          your NET.CFG (or SHELL.CFG) file to allocate additional
          stacks for IPX/SPX multi-tasking.

     3.)  For RCONSOLE, if all servers do not show up in the
          display, you need RCONSOLE v2.9, which is available for
          download from CompuServe/NetWire as RCNSLE.ZIP in
          NOVLIB Library 4.

System Hang-ups running NETBIOS applications under MS-Windows:

     1.)  Follow the same guidelines as described for running
          IPX/SPX applications under MS-Windows above.

     2.)  Include a statement "TimerCriticalSection=10000" under
          the [386Enh] section header of SYSTEM.INI.  This
          statement will help prevent deadlocks and re-entrancy
          problems associated when network activity is generated
          from a timer interrupt.

Cannot locate NETWARE.DLL error when loading NetWare Tools or
another application:

     1.)  See the "Recommendations for ALL Systems" section.
          There is no NETWARE.DLL, it is actually NETWARE.DRV,
          which is either not specified as
          "network.drv=netware.drv" under the [boot] section of
          SYSTEM.INI, or the NETWARE.DRV file is corrupt.

Remote Boot PCs cannot find WINA20.386:

     1.)  WINA20.386 is a DOS 5 file that is required for running
          MS-Windows 3.0 in enhanced mode with DOS=HIGH in the
          CONFIG.SYS.  (It is supposedly no longer used by
          MS-Windows 3.1.)

          MS-Windows looks for WINA20.386 when it is loading in the
          root of the boot drive *UNLESS* you include SWITCHES=/W
          in your CONFIG.SYS file, and specify
          "device=d:\path\WINA20.386" under the [386Enh] section
          header of SYSTEM.INI to tell MS-Windows where to find this
          driver.

Remote Boot PCs cannot find EMM386.EXE:

     1.)  If you are using the Microsoft EMM386.EXE device driver
          to provide expanded memory emulation, then be aware
          that MS-Windows needs to reload EMM386.EXE when MS-Windows is
          started to load a virtual device driver for upper
          memory management in 386 enhanced mode.

          MS-Windows looks for EMM386.EXE in the drive/directory
          that it was loaded from in CONFIG.SYS.  If you need to
          specify an alternate path, include a
          /y=d:\path\EMM386.EXE parameter when loading EMM386.EXE
          in CONFIG.SYS.  This path should be a path that will be
          valid when MS-Windows is later started.

Broadcast Messages do not display when in MS-Windows applications:

     1.)  Verify that NWPOPUP.EXE is included in the "load="
          statement of your WIN.INI file.

     2.)  In the Windows Control Panel, Network Options, ensure
          that the "Messages Enabled" button is clicked.

     3.)  See the "Recommendations for ALL Systems" section.

Broadcast Messages lock up MS-Windows:

     1.)  See the "Recommendations for ALL Systems" section.  In
          particular, focus on the GET LOCAL TARGET STACKS
          statement that should be placed in your NET.CFG (or
          SHELL.CFG) file.

          Ensure that this statement is echoed to the screen when
          IPX or IPXODI is loaded.

DOS DIR Command Shows No Files when used on Network Drives:

     1.)  See the "Recommendations for ALL Systems" section.  In
          particular, focus on the GET LOCAL TARGET STACKS
          statement that should be placed in your NET.CFG (or
          SHELL.CFG) file.

          Ensure that this statement is echoed to the screen when
          IPX or IPXODI is loaded.

How do I update to IPX.COM v3.10?:

     1.)  If you installed MS-Windows 3.1 for a Novell network, it
          should have copied an IPX.OBJ file to your
          Windows\SYSTEM directory.

          Copy this file to your WSGEN or SHGEN diskette, and re-
          run the WSGEN or SHGEN procedure to create an updated
          IPX.

          Now might be a good time to consider migrating to the
          IPX ODI drivers, which do not require this generating
          process, and are generally more up-to-date, as Novell
          is no longer certifying new drivers for the linkable
          IPX.COM.

          The IPX ODI drivers are included in the DOSUP5.ZIP file
          in NOVLIB Library 5 on CompuServe/NetWire, and
          documentation is included in ODIDOC.ZIP in this same
          library.

Controlling MS-Windows Swap Files:

     1.)  The following statements under the [386Enh] section
          header of SYSTEM.INI control the creation and placement
          of MS-Windows temporary swap files in 386 enhanced mode:

          Paging=Off (disables paging)
          MaxPagingFileSize=xxxx (max size of temporary swap file
          in KB)
          PagingDrive=d (paging files will be placed in the root
          of this drive)
          PagingFile=d:\path\SWAPFILE (MS-Windows 3.1 only: name to
          use for swap file, overrides PagingDrive entry)

     2.)  The following statement under the [NonWindowsApp]
          section of SYSTEM.INI controls the placement of swap
          files created when switching between DOS applications
          in MS-Windows Standard mode:

          SwapDisk=c:\path

          If this path is not specified, then MS-Windows will
          default to the directory pointed to by the TEMP DOS
          environmental variable (which many MS-Windows applications
          also use for controlling where they create temporary
          files), or the root directory of your first hard disk
          if the TEMP variable is not defined.

     3.)  The following statements under the [386Enh] section
          header of SYSTEM.INI control the location of permanent
          swap files (MS-Windows 3.1 Only):

          PermSwapDOSDrive=c (drive letter)
          PermSwapSizeK=xxxx (desired size of permanent swap
          file)

MS-Windows is very slow while loading:

     1.)  This is probably due to MS-Windows creating a temporary
          swap file when loading, possibly to a network drive.

          Under NetWare 2.x, this process is much slower than
          with NetWare 3.x.  See "Controlling MS-Windows Swap Files"
          above for more information.

Printing to a NetWare Print Queue results in 65,535 copies
requested:

     1.)  There are problems with the drivers for the current
          line of Intel 32 bit EISA network adapters.  Contact
          Intel to see if a fix is available, or use a different
          network adapter.

Loading NetWare MS-Windows Drivers when not attached to network
displays a warning message that the network is not present:

     1.)  Specify "NetWarn=0" under the [windows] section of your
          WIN.INI file, which tells MS-Windows not to warn you about
          loading network drivers when no network is present.

Garbage when printing from MS-Windows to a network printer:

     1.)  Are you running PSERVER?  If you are, then you need the
          latest and greatest version, v1.22.  PSERV1.ZIP can be
          downloaded from NOVLIB Library 6 on CompuServe/NetWire.

     2.)  What is your CAPTURE statement that you execute before
          going into MS-Windows?  You need to specify the NT (no tab
          expansion) flag, and I recommend a timeout of at least
          60 seconds (TI=60).  For PostScript printers, NB (no
          banner) and NFF (no form feed) are also necessary.  NA
          (no autoendcap) is also required in some MS-Windows
          configurations.

          The NA flag will cause you some problems if you are
          printing to LPTx.OS2 (or LPTx.DOS in MS-Windows 3.1)
          instead of LPTx.  While previous recommendations were
          to print to LPTx.OS2, these recommendations have been
          superseded because of updated Novell drivers.

          If you are using all MS-Windows applications, you should
          be able to set TI=0 to disable the timeout feature, as
          it is not necessary if applications print through the
          standard MS-Windows APIs.

     3.)  In the Windows Control Panel/Printers/Configure menu,
          disable the print manager if it is not already
          disabled.  (Since NetWare print jobs are spooled to
          disk anyway, using the print manager when spooling to a
          network printer is redundant and can slow things down.)

     4.)  Make sure that you have the latest NetWare drivers for
          MS-Windows.  For MS-Windows 3.1, the drivers that ship with
          the product are satisfactory.  For MS-Windows 3.0, you
          need VNETWARE.386 v2.0, the version that is included in
          the WINUP6.ZIP file in NOVLIB Library 5 on
          CompuServe/NetWire.

     5.)  Type CAPTURE SHOW in a DOS Window after going into
          MS-Windows, and make sure that these settings are the same
          as what were set before going into MS-Windows.  A MS-Windows
          "permanent list" setting can override the CAPTURE that
          you set before going into MS-Windows.  Check the [network]
          section of your WIN.INI and delete any statements that
          reference print captures to avoid confusion.

     6.)  When all else fails, try connecting the printer to the
          workstation directly to verify that this is indeed a
          network problem.

MS-Windows hangs when opening a DOS Window or DOS application:

     1.)  Make sure that you have the NetWare drivers for MS-Windows
          loaded:  "network.drv=netware.drv" under the [boot]
          section of SYSTEM.INI, and for 386 enhanced mode,
          "network.drv=vnetware.386" (*vnetbios & vipx.386 may
          also be specified in this command) under the [386Enh]
          section of SYSTEM.INI.

     2.)  For MS-Windows 3.0, is your network card set to IRQ 2 or
          9, 10 or higher?  If it is, then you will need to
          install the VPICDA.386 patch (included in WINUP5.ZIP in
          NOVLIB on CompuServe).  Copy VPICDA.386 into your
          Windows\SYSTEM directory, and edit your SYSTEM.INI,
          replacing the line "device=*vpicd" with
          "device=vpicda.386".

          NOTE:  VPICDA.386 is not required for MS-Windows 3.1, you
          should specify "device=*vpicd" instead.

     3.)  You may be running out of file handles.  Increase the
          value specified in the FILE HANDLES statement in your
          NET.CFG (or SHELL.CFG) file.

     4.)  You may be experiencing swap file corruption.  Refer to
          the section entitled "Controlling MS-Windows Swap Files"
          to ensure that swap files are being created in the
          correct locations.  (If you are swapping to the
          network, swap files must be stored in unique
          directories.)

     5.)  A TSR that you are running may require that you specify
          "TimerCriticalSection=10000" under the [386Enh] section
          header of your SYSTEM.INI

DOS Environment Missing or Corrupt in DOS windows:

     1.)  Make sure that you have the NetWare drivers for MS-Windows
          loaded:  "network.drv=netware.drv" under the [boot]
          section of SYSTEM.INI, and for 386 enhanced mode,
          "network.drv=vnetware.386" (*vnetbios & vipx.386 may
          also be specified in this command) under the [386Enh]
          section of SYSTEM.INI.

     2.)  Verify that your NetWare drivers are up to date.
          Review "Recommendations for ALL systems" in this
          document.

Changing directories on a network drive in one window affects all
windows:

     1.)  If you have NWShareHandles=TRUE in the [NetWare]
          section of your WIN.INI file, then this is what is
          causing the problem.

     2.)  If you have a TASK MODE = statement in your NET.CFG (or
          SHELL.CFG) file, then this is what is causing the
          problem.

NetWare MENU program freezes or performs erratically (like you
would notice <g>) after executing MS-Windows from a menu option:

     1.)  This is a known incompatibility, and there is not a fix
          at this time.

RPRINTER and MS-Windows:

     1.)  These don't peacefully co-exist at this time, and the
          best solution is to purchase a 3rd party alternative.
          Alternatives include hardware based solutions like
          network cards installed in laser printers, as well as
          the Castelle LanPress and Intel NetPort.  Software
          solutions like Fresh Technologies Printer Assist and
          Intel's LanSpool are also reported to work.

          If you want to try RPRINTER, you can also experiment
          with the following suggestions.

     2.)  Run MS-Windows in Standard Mode (WIN /S) on PCs that are
          running RPRINTER.

     3.)  Disable the MS-Windows print manager.

     4.)  Try increasing the SPX timeout values specified in your
          NET.CFG (or SHELL.CFG).  For example:

          SPX ABORT TIMEOUT = 4000
          SPX LISTEN TIMEOUT = 2500

     5.)  Try installing Microsoft's VPD.386 driver as
          "device=vpd.386" under the [386Enh] section header of
          SYSTEM.INI.  This driver can be downloaded from the
          Microsoft Software Library on CompuServe (GO MSL) under
          the filename VPD386.EXE.

     6.)  Review "Recommendations for ALL Systems" to ensure that
          you have the latest drivers and proper configuration
          support.

Undocumented Option for Changing Drives and Printers Built into
NetWare Drivers

      There is an undocumented option built into NETWARE.DRV that
      gives you hot-key access to a dialog that allows you to
      change drive mappings, print queue assignments, and
      attach/detach to other servers in your network.

      Under the [options] section of your NETWARE.INI file,
      include a statement "NetWareHotKey=123".

      Restart MS-Windows and press F12.  Any time you press F12, it
      will pop-up a selection menu that gives you access to a
      menu of NetWare functions.  Do not minimize this window or
      switch away from it while active, or the application that
      you popped this window up over will no longer be able to
      receive keystrokes.

Where to Go For More Information

      "Running MS-Windows on NetWare" by Stephen Saxon from M&T
      Books

      "Networking MS-Windows: NetWare Edition" by Howard Marks,
      Kristin Marks and Rick Segal from Sams Books

      "Microsoft Windows Resource Kit" from Microsoft

      "MS-Windows 3.1 Secrets" by Brian Livingston

      NOVB Section 15 in the NetWire Family of Forums on
      CompuServe

Thanks to Brett Warthen of Infinite Technologies for the material in
the last section.